home *** CD-ROM | disk | FTP | other *** search
/ IRIX Base Documentation 1998 November / IRIX 6.5.2 Base Documentation November 1998.img / usr / share / catman / p_man / cat4 / netconfig.z / netconfig
Text File  |  1998-10-20  |  16KB  |  264 lines
  1.  
  2.  
  3.  
  4. nnnneeeettttccccoooonnnnffffiiiigggg((((4444))))                                                      nnnneeeettttccccoooonnnnffffiiiigggg((((4444))))
  5.  
  6.  
  7.  
  8. NNNNAAAAMMMMEEEE
  9.      _nnnn_eeee_tttt_cccc_oooo_nnnn_ffff_iiii_gggg - network configuration database
  10.  
  11. SSSSYYYYNNNNOOOOPPPPSSSSIIIISSSS
  12.      _####_iiii_nnnn_cccc_llll_uuuu_dddd_eeee _<<<<_nnnn_eeee_tttt_cccc_oooo_nnnn_ffff_iiii_gggg_...._hhhh_>>>>
  13.  
  14. DDDDEEEESSSSCCCCRRRRIIIIPPPPTTTTIIIIOOOONNNN
  15.      The network configuration database, _////_eeee_tttt_cccc_////_nnnn_eeee_tttt_cccc_oooo_nnnn_ffff_iiii_gggg, is a system file used
  16.      to store information about networks connected to the system and available
  17.      for use.  The _nnnn_eeee_tttt_cccc_oooo_nnnn_ffff_iiii_gggg database and the routines that access it [see
  18.      _gggg_eeee_tttt_nnnn_eeee_tttt_cccc_oooo_nnnn_ffff_iiii_gggg(3N)] are part of the UNIX System V Network Selection
  19.      component.  The Network Selection component also includes the environment
  20.      variable _NNNN_EEEE_TTTT_PPPP_AAAA_TTTT_HHHH and a group of routines that access the _nnnn_eeee_tttt_cccc_oooo_nnnn_ffff_iiii_gggg
  21.      database using _NNNN_EEEE_TTTT_PPPP_AAAA_TTTT_HHHH components as links to the _nnnn_eeee_tttt_cccc_oooo_nnnn_ffff_iiii_gggg entries.
  22.      _NNNN_EEEE_TTTT_PPPP_AAAA_TTTT_HHHH is described in _ssss_hhhh(1); the _NNNN_EEEE_TTTT_PPPP_AAAA_TTTT_HHHH access routines are discussed
  23.      in _gggg_eeee_tttt_nnnn_eeee_tttt_pppp_aaaa_tttt_hhhh(3N).
  24.  
  25.      _nnnn_eeee_tttt_cccc_oooo_nnnn_ffff_iiii_gggg contains an entry for each network available on the system.
  26.      Entries are separated by newlines.  Fields are separated by whitespace
  27.      and occur in the order in which they are described below.  Whitespace can
  28.      be embedded as ``_\\\\_b_l_a_n_k'' or ``_\\\\_t_a_b''.  Backslashes may be embedded as
  29.      ``_\\\\_\\\\''.  Each field corresponds to an element in the _ssss_tttt_rrrr_uuuu_cccc_tttt _nnnn_eeee_tttt_cccc_oooo_nnnn_ffff_iiii_gggg
  30.      structure.  _ssss_tttt_rrrr_uuuu_cccc_tttt _nnnn_eeee_tttt_cccc_oooo_nnnn_ffff_iiii_gggg and the identifiers described on this manual
  31.      page are defined in _////_uuuu_ssss_rrrr_////_iiii_nnnn_cccc_llll_uuuu_dddd_eeee_////_nnnn_eeee_tttt_cccc_oooo_nnnn_ffff_iiii_gggg_...._hhhh.
  32.  
  33.      _n_e_t_w_o_r_k _I_D
  34.            A string used to uniquely identify a network.  _n_e_t_w_o_r_k _I_D consists
  35.            of non-null characters, and has a length of at least 1.  No maximum
  36.            length is specified.  This namespace is locally significant and the
  37.            local system administrator is the naming authority.  All _n_e_t_w_o_r_k
  38.            _I_Ds on a system must be unique.
  39.  
  40.      _s_e_m_a_n_t_i_c_s
  41.            The _s_e_m_a_n_t_i_c_s field is a string identifying the ``semantics'' of
  42.            the network, i.e., the set of services it supports, by identifying
  43.            the service interface it provides.  The _s_e_m_a_n_t_i_c_s field is
  44.            mandatory.  The following semantics are recognized.
  45.  
  46.                _tttt_pppp_iiii______cccc_llll_tttt_ssss    Transport Provider Interface, connectionless
  47.  
  48.                _tttt_pppp_iiii______cccc_oooo_tttt_ssss    Transport Provider Interface, connection oriented
  49.  
  50.                _tttt_pppp_iiii______cccc_oooo_tttt_ssss______oooo_rrrr_dddd
  51.                            Transport Provider Interface, connection oriented,
  52.                            supports orderly release.
  53.  
  54.                _tttt_pppp_iiii______rrrr_aaaa_wwww     Transport Provider Interface, raw
  55.  
  56.      _f_l_a_g  The _f_l_a_g field records certain two-valued (``true'' and ``false'')
  57.            attributes of networks.  _f_l_a_g is a string composed of a combination
  58.            of characters, each of which indicates the value of the
  59.            corresponding attribute.  If the character is present, the
  60.  
  61.  
  62.  
  63.                                                                         PPPPaaaaggggeeee 1111
  64.  
  65.  
  66.  
  67.  
  68.  
  69.  
  70. nnnneeeettttccccoooonnnnffffiiiigggg((((4444))))                                                      nnnneeeettttccccoooonnnnffffiiiigggg((((4444))))
  71.  
  72.  
  73.  
  74.            attribute is ``true.''  If the character is absent, the attribute
  75.            is ``false.''  ``_----'' indicates that none of the attributes is
  76.            present.  Only one character is currently recognized:
  77.  
  78.                _vvvv           Visible (``default'') network.  Used when the
  79.                            environment variable _NNNN_EEEE_TTTT_PPPP_AAAA_TTTT_HHHH is unset.
  80.  
  81.      _p_r_o_t_o_c_o_l _f_a_m_i_l_y
  82.            The _p_r_o_t_o_c_o_l _f_a_m_i_l_y and _p_r_o_t_o_c_o_l _n_a_m_e fields are provided for
  83.            protocol-specific applications.
  84.            The _p_r_o_t_o_c_o_l _f_a_m_i_l_y field contains a string that identifies a
  85.            protocol family.  The _p_r_o_t_o_c_o_l _f_a_m_i_l_y identifier follows the same
  86.            rules as those for _n_e_t_w_o_r_k _I_Ds, that is, the string consists of
  87.            non-null characters; it has a length of at least _1111; and there is no
  88.            maximum length specified.  A ``_----'' in the _p_r_o_t_o_c_o_l _f_a_m_i_l_y field
  89.            indicates that no protocol family identifier applies, that is, the
  90.            network is experimental.  The following are examples:
  91.  
  92.                _llll_oooo_oooo_pppp_bbbb_aaaa_cccc_kkkk    Loopback (local to host).
  93.                _iiii_nnnn_eeee_tttt        Internetwork: UDP, TCP, etc.
  94.                _iiii_mmmm_pppp_llll_iiii_nnnn_kkkk     ARPANET imp addresses
  95.                _pppp_uuuu_pppp         PUP protocols: e.g. BSP
  96.                _cccc_hhhh_aaaa_oooo_ssss       MIT CHAOS protocols
  97.                _nnnn_ssss          XEROX NS protocols
  98.                _nnnn_bbbb_ssss         NBS protocols
  99.                _eeee_cccc_mmmm_aaaa        European Computer Manufacturers Association
  100.                _dddd_aaaa_tttt_aaaa_kkkk_iiii_tttt     DATAKIT protocols
  101.                _cccc_cccc_iiii_tttt_tttt       CCITT protocols, X.25, etc.
  102.                _ssss_nnnn_aaaa         IBM SNA
  103.                _dddd_eeee_cccc_nnnn_eeee_tttt      DECNET
  104.                _dddd_llll_iiii         Direct data link interface
  105.                _llll_aaaa_tttt         LAT
  106.                _hhhh_yyyy_llll_iiii_nnnn_kkkk      NSC Hyperchannel
  107.                _aaaa_pppp_pppp_llll_eeee_tttt_aaaa_llll_kkkk   Apple Talk
  108.                _nnnn_iiii_tttt         Network Interface Tap
  109.                _iiii_eeee_eeee_eeee_8888_0000_2222     IEEE 802.2; also ISO 8802
  110.                _oooo_ssss_iiii         Umbrella for all families used by OSI (e.g.,
  111.                            protosw lookup)
  112.                _xxxx_2222_5555         CCITT X.25 in particular
  113.                _oooo_ssss_iiii_nnnn_eeee_tttt      AFI = 47, IDI = 4
  114.                _gggg_oooo_ssss_iiii_pppp       U.S. Government OSI
  115.  
  116.      _p_r_o_t_o_c_o_l _n_a_m_e
  117.            The _p_r_o_t_o_c_o_l _n_a_m_e field contains a string that identifies a
  118.            protocol.  The _p_r_o_t_o_c_o_l _n_a_m_e identifier follows the same rules as
  119.            those for _n_e_t_w_o_r_k _I_Ds, that is, the string consists of non-NULL
  120.            characters; it has a length of at least _1111; and there is no maximum
  121.            length specified.  The following protocol names are recognized.  A
  122.            ``_----'' indicates that none of the names listed applies.
  123.  
  124.  
  126.  
  127.  
  128.                                                                         PPPPaaaaggggeeee 2222
  129.  
  130.  
  131.  
  132.  
  133.  
  134.  
  135. nnnneeeettttccccoooonnnnffffiiiigggg((((4444))))                                                      nnnneeeettttccccoooonnnnffffiiiigggg((((4444))))
  136.  
  137.  
  138.  
  139.                _tttt_cccc_pppp     Transmission Control Protocol
  140.  
  141.                _uuuu_dddd_pppp     User Datagram Protocol
  142.  
  143.                _iiii_cccc_mmmm_pppp    Internet Control Message Protocol
  144.  
  145.      _n_e_t_w_o_r_k _d_e_v_i_c_e
  146.            The _n_e_t_w_o_r_k _d_e_v_i_c_e is the full pathname of the device used to
  147.            connect to the transport provider.  Typically, this device will be
  148.            in the _////_dddd_eeee_vvvv directory.  The _n_e_t_w_o_r_k _d_e_v_i_c_e  must be specified.
  149.  
  150.      _d_i_r_e_c_t_o_r_y _l_o_o_k_u_p _l_i_b_r_a_r_i_e_s
  151.            The _d_i_r_e_c_t_o_r_y _l_o_o_k_u_p _l_i_b_r_a_r_i_e_s support a ``directory service'' (a
  152.            name-to-address mapping service) for the network.  This service is
  153.            implemented by the UNIX System V Name-to-Address Mapping feature.
  154.            If a network is not provided with such a library, the _n_e_t_d_i_r
  155.            feature will not work.  A ``_----'' in this field indicates the absence
  156.            of any lookup libraries, in which case name-to-address mapping for
  157.            the network is non-functional.  The directory lookup library field
  158.            consists of a comma-separated list of full pathnames to dynamically
  159.            linked libraries.  Commas may be embedded as ``_\\\\_,,,,''; backslashs as
  160.            ``_\\\\_\\\\''.
  161.  
  162.      Lines in _////_eeee_tttt_cccc_////_nnnn_eeee_tttt_cccc_oooo_nnnn_ffff_iiii_gggg that begin with a sharp sign (_####) in column 1 are
  163.      treated as comments.
  164.  
  165.      The _ssss_tttt_rrrr_uuuu_cccc_tttt _nnnn_eeee_tttt_cccc_oooo_nnnn_ffff_iiii_gggg structure includes the following members
  166.      corresponding to the fields in the _nnnn_eeee_tttt_cccc_oooo_nnnn_ffff_iiii_gggg database entries:
  167.  
  168.      _cccc_hhhh_aaaa_rrrr _**** _nnnn_cccc______nnnn_eeee_tttt_iiii_dddd                  Network ID, including NULL terminator
  169.  
  170.      _uuuu_nnnn_ssss_iiii_gggg_nnnn_eeee_dddd _llll_oooo_nnnn_gggg _nnnn_cccc______ssss_eeee_mmmm_aaaa_nnnn_tttt_iiii_cccc_ssss       Semantics
  171.  
  172.      _uuuu_nnnn_ssss_iiii_gggg_nnnn_eeee_dddd _llll_oooo_nnnn_gggg _nnnn_cccc______ffff_llll_aaaa_gggg            Flags
  173.  
  174.      _cccc_hhhh_aaaa_rrrr _**** _nnnn_cccc______pppp_rrrr_oooo_tttt_oooo_ffff_mmmm_llll_yyyy              Protocol family
  175.  
  176.      _cccc_hhhh_aaaa_rrrr _**** _nnnn_cccc______pppp_rrrr_oooo_tttt_oooo                  Protocol name
  177.  
  178.      _cccc_hhhh_aaaa_rrrr _**** _nnnn_cccc______dddd_eeee_vvvv_iiii_cccc_eeee                 Full pathname of the network device
  179.  
  180.      _uuuu_nnnn_ssss_iiii_gggg_nnnn_eeee_dddd _llll_oooo_nnnn_gggg _nnnn_cccc______nnnn_llll_oooo_oooo_kkkk_uuuu_pppp_ssss        Number of directory lookup libraries
  181.  
  182.      _cccc_hhhh_aaaa_rrrr _****_**** _nnnn_cccc______llll_oooo_oooo_kkkk_uuuu_pppp_ssss               Full pathnames of the directory lookup
  183.                                       libraries themselves
  184.  
  185.      _uuuu_nnnn_ssss_iiii_gggg_nnnn_eeee_dddd _llll_oooo_nnnn_gggg _nnnn_cccc______uuuu_nnnn_uuuu_ssss_eeee_dddd_[[[[_9999_]]]]       Reserved for future expansion (not
  186.                                       advertised to user level)
  187.  
  188.      The _nnnn_cccc______ssss_eeee_mmmm_aaaa_nnnn_tttt_iiii_cccc_ssss field takes the following values, corresponding to the
  189.      semantics identified above:
  190.  
  191.  
  192.  
  193.  
  194.                                                                         PPPPaaaaggggeeee 3333
  195.  
  196.  
  197.  
  198.  
  199.  
  200.  
  201. nnnneeeettttccccoooonnnnffffiiiigggg((((4444))))                                                      nnnneeeettttccccoooonnnnffffiiiigggg((((4444))))
  202.  
  203.  
  204.  
  205.            _NNNN_CCCC______TTTT_PPPP_IIII______CCCC_LLLL_TTTT_SSSS
  206.            _NNNN_CCCC______TTTT_PPPP_IIII______CCCC_OOOO_TTTT_SSSS
  207.            _NNNN_CCCC______TTTT_PPPP_IIII______CCCC_OOOO_TTTT_SSSS______OOOO_RRRR_DDDD
  208.            _NNNN_CCCC______TTTT_PPPP_IIII______RRRR_AAAA_WWWW
  209.  
  210.      The _nnnn_cccc______ffff_llll_aaaa_gggg field is a bitfield.  The following bit, corresponding to the
  211.      attribute identified above, is currently recognized. _NNNN_CCCC______NNNN_OOOO_FFFF_LLLL_AAAA_GGGG indicates
  212.      the absence of any attributes.
  213.  
  214.            _NNNN_CCCC______VVVV_IIII_SSSS_IIII_BBBB_LLLL_EEEE
  215.  
  216. FFFFIIIILLLLEEEESSSS
  217.      _////_eeee_tttt_cccc_////_nnnn_eeee_tttt_cccc_oooo_nnnn_ffff_iiii_gggg
  218.      _////_uuuu_ssss_rrrr_////_iiii_nnnn_cccc_llll_uuuu_dddd_eeee_////_nnnn_eeee_tttt_cccc_oooo_nnnn_ffff_iiii_gggg_...._hhhh
  219.  
  220. SSSSEEEEEEEE AAAALLLLSSSSOOOO
  221.      _nnnn_eeee_tttt_dddd_iiii_rrrr______gggg_eeee_tttt_bbbb_yyyy_nnnn_aaaa_mmmm_eeee(3N), _gggg_eeee_tttt_nnnn_eeee_tttt_cccc_oooo_nnnn_ffff_iiii_gggg(3N), _gggg_eeee_tttt_nnnn_eeee_tttt_pppp_aaaa_tttt_hhhh(3N), _nnnn_eeee_tttt_cccc_oooo_nnnn_ffff_iiii_gggg(4),
  222.      _iiii_cccc_mmmm_pppp(7), _iiii_pppp(7)
  223.  
  224.  
  225.  
  226.  
  227.  
  228.  
  229.  
  230.  
  231.  
  232.  
  233.  
  234.  
  235.  
  236.  
  237.  
  238.  
  239.  
  240.  
  241.  
  242.  
  243.  
  244.  
  245.  
  246.  
  247.  
  248.  
  249.  
  250.  
  251.  
  252.  
  253.  
  254.  
  255.  
  256.  
  257.  
  258.  
  259.  
  260.                                                                         PPPPaaaaggggeeee 4444
  261.  
  262.  
  263.  
  264.